A pattern for building personal knowledge bases using LLMs.

This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.

Written by the speakers and attendees of AIE Code Summit 2026

In 2001, 17 software engineers and leaders got together at a ski lodge in Snowbird, Utah to understand the biggest challenge of their time: heavyweight, documentation-driven software development processes.

Out of this we got the Agile Manifesto, four values and twelve principles that changed how most of the industry builds software.

Today we convene to build our own manifesto - the No AI Slop manifesto.

Author: Kobus Wentzel (@kobie3717)
Discovered: April 18, 2026
Status: Fully tested and documented

WhatsApp accepts messages to arbitrarily crafted JIDs (e.g., 99999000001@s.whatsapp.net) even when no account exists for that "number." The result: a persistent 1:1 chat thread appears on the sender's device with a phone number that has no SIM card, no registration, and no real WhatsApp account. We also discovered that Baileys silently caches device-level LID (Linked Device ID) mappings from group interactions, enabling direct device-to-device message routing.

Worker agents (server-coder, client-coder, client-ui, client-lang, infra-coder): You are an implementation agent. You write code, run verification, report back.

• Read: # Code Philosophy, # Agent Directives, # Rules
• SKIP everything under # orchestrate — that is coordinator-only
• NEVER run anakmagang commands, spawn sub-agents, track phases, or reflect on meta-cognitive questions
• Your job: implement → verify → emit completion signal (IMPLEMENTATION_COMPLETE / VERIFICATION_FAILED / etc.)

X → Graph → Effect<A, E, R>
│              │   │  │  │
│              │   │  │  └─ what each node needs     (§5)
│              │   │  └──── where the graph breaks   (§4)
│              │   └─────── what flows through nodes  (§2)
│              │
│ └─ nodes = functions, edges = data flow